Here is the setup:6 exchange 2003 servers, mail-sd1 - mail-sd6.3 Exchange 2010 servers, mail-sd01 (mailbox role) mail-owa01 (client access role) mail-hub01 (hub transport role)I have two accounts on the mail-sd01 server, both accounts can send emails to all users except for users on mail-sd2. when sending an email to a user that resides on mail-sd2, they receive a 5.2.1 bounce message generated by mail-sd2. This happens when using Outlook 2003 and Outlook 2007, but NOT when using Outlook Web App.When reviewing the headers for the emails that are sent via the Outlook Web app, they appear to follow the same path as an email sent via outlook.Sending an email manually tousers on mail-sd2by using telnet to port 25from mail-sd01 to mail-hub01 server is successful.When the NDR is generated by mail-sd2, mail-sd2 generates an Event ID 3013, which lists the possible cause 1) Local mail delivery was denied because the message size was too large. 2) the recipients mailbox has been disabled.Subject of the mail is "test" Body of the test email is "grr"Any suggestions as to how to troubleshoot this issue? Has anyone seen this?Loren

Loren, I hope this is in a lab environment because E2K10 is still beta software.Anyways, that being said, a TELNET test is useful, but also often too primitive toprovide an accurate test. You have a routing group connector from MAIL-HUB01 to the E2K3 routing group. Which E2K3 server is functioning as the bridgehead server? Is it MAIL-SD2? What happens if you move the bridgehead to another server? Can you post the SMTP headers here for a message that goes frmo MAIL-SD2 to MAIL-SD01?JimJim McBee - Blog - http://mostlyexchange.blogspot.com

Jim,mail-sd5 is the server functioning as the bridgehead server for this connector.While getting you the information, I noticed that mail-sd2 was getting a bunch of 9667 errors (Failed to create a new named property for database ***, because the number of named properties reached the quota limit (8192)). We've had this issue in the past, so we increased the property limitto 16384, restarted the Exchange server services.. and everything is working normally. Users on mail-sd01 can nowsend emails to users on mail-sd2 (and all of the other servers). So right now, mail is flowing in all directions.I'll have to read up on named properties and how this would have effected Outlook clients but NOT the Exchange Web App.Thank you for your time.Loren

Loren, Thanks for your post. I just ran into the exact same problem during an Exchange 2003 to Exchange 2010 migration. I changed the quota for NonMAPI Names Props from 8192 to 16384 on the Exchange 2003 server, restarted the Exchange Information Store service, and all was working. This was a very big help, and not something I would have suspected otherwise. Chris

Anyone who have a similar issue should look at this as we ran into a similar issue at a customer site. The quota has to be increased and how to do it is mentioned in the following link. http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/be90453d-c028-4a02-a5d3-f4eaa1a7556e?prof=required The exact Microsoft article can be found here http://technet.microsoft.com/en-us/library/bb851493%28EXCHG.80%29.aspx

This is truly embarrassing that Microsoft has customers changing the registry on production 2003 servers so that you can simply send an email from an outlook client.